chore(cli): re-pin go-flashduty to merged main (follow-up to #52)#54
Merged
Conversation
#52 merged at the pre-re-pin commit, so feat/ai-sre pinned the go-flashduty#11 PR-branch commit (da82c4) rather than the squash-merged main commit. Re-pin to go-flashduty main (54d4fc1) so the dependency tracks main, not an orphaned PR-branch commit kept alive only by the closed PR. Generated output unchanged (identical spec); build + unit tests pass.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up hygiene fix to #52.
#52 was merged at its pre-re-pin commit, so
feat/ai-sreended up pinning the go-flashduty#11 PR-branch commit (da82c4) instead of the squash-merged main commit (54d4fc1). That orphaned commit currently resolves only because the closed PR keeps it alive — fragile.This re-pins go.mod to go-flashduty
main. Generatedzz_generated_*is unchanged (identical spec content), so the diff is go.mod/go.sum only.go build+go test ./internal/...pass; cligen re-run produces no drift.